System and method for rejoining a traffic log mode after a breakout in a broadcasting environment

ABSTRACT

Disclosed herein is a system and method for rejoining a traffic log mode after a breakout in a broadcasting environment. One example method involves (i) receiving a traffic log including traffic log entries, each corresponding to a VC and a start time; (ii) operating in a traffic log mode; (iii) receiving a breakout-mode request; (iv) responsive to receiving the breakout-mode request, (a) terminating operation of the traffic log mode, (b) generating a simulation log, and (c) operating in a breakout mode; (v) receiving a rejoin request; (vi) determining a breakout termination time based on the received rejoin request; (vii) proximate the breakout termination time, terminating operation of the breakout-mode, and operating in a custom log mode; (viii) determining a rejoin position of the traffic log based on the received rejoin request; and (ix) operating in the traffic log mode.

CROSS REFERENCE TO RELATED APPLICATIONS

This disclosure claims priority to U.S. Provisional Patent ApplicationSer. No. 61/542,103, entitled “System and Method for a MasterController,” filed on Sep. 30, 2011, which is hereby incorporated byreference herein in its entirety.

This disclosure also relates to U.S. patent application Ser. No.13/629,519, entitled “System and Method for Extending a Breakout in aBroadcasting Environment,” which is assigned to the assignee of thepresent disclosure, which is being filed simultaneously, and which ishereby incorporated by reference herein in its entirety.

USAGE AND TERMINOLOGY

Throughout this application, with respect to all reasonable derivativesof such terms, and unless otherwise specified (and/or unless theparticular context clearly dictates otherwise), each usage of:

-   -   “a” or “an” is meant to read as “at least one.”    -   “the” is meant to be read as “the at least one.”    -   the term “video” refers broadly to any material represented in a        video format (i.e., having a plurality of frames). In some        instances, video may include a plurality of sequential frames        that are identical or nearly identical, and that may give the        impression of a “still” image. Video may or may not include an        audio portion.    -   the term “audio” refers broadly to any material represented in        an audio format.    -   The term “media-component” (MC) refers to video or audio that        one of ordinary skill in the art would typically consider to be        self-contained, and that is typically separately scheduled by a        traffic system in a broadcasting environment.    -   the term “video-component” (VC) refers to a particular type of        MC, namely one that includes video, and that is typically        separately scheduled by a traffic system in a        television-broadcasting environment. There are several types of        VCs, including, for example, a show-segment VC, such as a        six-minute segment of a news program or a five-minute segment of        an episode of a sitcom. Another example type of VC is a        commercial VC, such as a thirty-second advertisement for a        product. Yet another example type of VC is a promotion VC, such        as a fifteen-second promotion for a news program.    -   The term “audio-component” (AC) refers to a particular type of        MC, namely one that contains audio, and that is typically        separately scheduled by a scheduling traffic system in a        radio-broadcasting environment. Similar to a VC, there are        several types of ACs, including for example a show-segment AC,        such as a six-minute segment of a news program. Another example        type of AC is a commercial AC, such as a thirty-second        advertisement for a product. Yet another example type of AC is a        promotion AC, such as a fifteen-second promotion for a news        program.

TECHNICAL FIELD

The presently disclosed system and method relates to broadcastingtechnology, inducing for example, television-broadcasting andradio-broadcasting technology.

BACKGROUND

In the field of television broadcasting, traffic systems are softwareand/or hardware packages that may be used, among other things, toschedule and sequence VCs intended for broadcast (e.g., over the air).To schedule VCs, a traffic manager may interact with the traffic systemto create a traffic log. A traffic log may indicate which VCs areintended to be broadcast during a particular time span, and further mayindicate when each VC is intended to be broadcast. A traffic log mayinclude multiple traffic log entries, with each traffic log entrycorresponding to one VC and scheduling data for that VC. The traffic logtherefore may represent the sequence of VCs intended to be broadcastduring the time span. The traffic log may take the form of a table orother data structure.

A traffic system typically communicates with a master control system(MCS), which is the technical hub of a broadcast operation and is thefinal point before a VC is sent to an air-chain system for broadcast.More specifically, the traffic system typically communicates with anautomation system (AS) of the MCS. The AS is the logic center of the MCSand may cause the MCS and/or another entity to perform variousfunctions. Through a communication path, the traffic system may providethe traffic log to the AS, such that the AS may traverse and selecttraffic log entries according to their corresponding scheduling data.The AS may then cause the MCS and/or another entity to perform certainfunctions corresponding to each selected traffic log entry. Suchfunctions typically include the MCS retrieving from a data storage theVC corresponding to the traffic log entry, channeling the VC through oneor more entities within the MCS (e.g., through one or more switches),and sending the VC to an air-chain system for broadcast.

SUMMARY

In one aspect, a method for sending video to an air-chain system fortelevision broadcast is disclosed. The method involves: (i) receivingfrom a traffic system, a traffic log including traffic log entries, eachcorresponding to a VC and a start time; (ii) operating in a traffic logmode including: traversing the traffic log entries according to thecorresponding start times and a running time, and sending the VCscorresponding to the traversed traffic log entries to the air-chainsystem in sequence; (iii) receiving a breakout-mode request; (iv)responsive to receiving the breakout-mode request, (a) terminatingoperation of the traffic log mode, (b) generating a simulation log thatincludes simulation entries, and that is a copy of at least a portion ofthe traffic log, and (c) operating in a breakout mode including: sendingvideo received from a breakout source to the air-chain system,traversing the simulation entries according to the corresponding starttimes and the time, generating a missed list that indicates the VCscorresponding to the traversed simulation entries, and generating acustom log that indicates at least a portion of the VCs in the generatedmissed list; (v) receiving a rejoin request; (vi) determining a breakouttermination time based on the received rejoin request; (vii) proximatethe breakout termination time, terminating operation of thebreakout-mode, and operating in a custom log mode including traversingand sending the VCs indicated in the generated custom log to theair-chain system in sequence; (viii) determining a rejoin position ofthe traffic log based on the received rejoin request; and (ix) operatingin the traffic log mode, wherein the traffic log entries are traversedstarting at the determined rejoin position.

In another aspect, a non-transitory computer-readable medium containinginstructions that, when executed by a processor, cause a set offunctions to be performed is disclosed. The set includes the functionsdescribed one paragraph above this one.

In another aspect, a method for sending audio to an air-chain system forradio broadcast is disclosed. The method involves: (i) receiving from atraffic system, a traffic log including traffic log entries, eachcorresponding to an audio component (AC) and a start time; (ii)operating in a traffic log mode including: traversing the traffic logentries according to the corresponding start times and a running time,and sending the ACs corresponding to the traversed traffic log entriesto the air-chain system in sequence; (iii) receiving a breakout-moderequest; (iv) responsive to receiving the breakout-mode request, (a)terminating operation of the traffic log mode, (b) generating asimulation log that includes simulation entries, and that is a copy ofat least a portion of the traffic log, and (c) operating in a breakoutmode including: sending audio received from a breakout source to theair-chain system, traversing the simulation entries according to thecorresponding start times and the time, generating a missed list thatindicates the ACs corresponding to the traversed simulation entries, andgenerating a custom log that indicates at least a portion of the ACs inthe generated missed list; (v) receiving a rejoin request; (vi)determining a breakout termination time based on the received rejoinrequest; (vii) proximate the breakout termination time, terminatingoperation of the breakout-mode, and operating in a custom log modeincluding traversing and sending the ACs indicated in the generatedcustom log to the air-chain system in sequence; (viii) determining arejoin position of the traffic log based on the received rejoin request;and (ix) operating in the traffic log mode, wherein the traffic logentries are traversed starting at the determined rejoin position.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified block diagram of an example television-broadcastsystem.

FIG. 2 is a simplified block diagram of an example traffic system.

FIG. 3 is a simplified block diagram of an example recording and playoutsystem.

FIG. 4 is a simplified block diagram of an example master controlsystem.

FIG. 5 is a simplified block diagram of an example air-chain system.

FIG. 6 (parts A and B) is a simplified block diagram of functions of anexample method.

FIG. 7 shows a set of timelines illustrating an example use of a rejoinin progress technique.

FIG. 8 shows a set of timelines illustrating an example use of a rejoinat a forced start of a show-segment video component technique.

FIG. 9 shows a set of timelines illustrating an example us of a rejoinat a natural start of a show-segment video component technique.

DETAILED DESCRIPTION OF THE DRAWINGS I. Overview

In the television-broadcasting industry, traffic systems are provided bymultiple vendors and often include distinguishing features. However, fora variety of reasons such as to provide compatibility, many trafficsystems create logs according to a general industry-wide standard.Likewise, many ASs are configured to receive logs based on thisstandard. A traffic log entry based on this standard typically includescertain attributes. These attributes may be generated automatically(e.g., by the traffic system) or may be provided by a traffic manager.

One such attribute is a house number, which identifies the VC thatcorresponds to the traffic log entry. Typically, the house number is aunique identifier within a broadcasting system and maps to a filelocation in a data storage where the VC is stored. As such, by obtainingthe house number, the AS may use a mapping table to determine thecorresponding file location, and may then retrieve the VC stored in thatfile location. Two examples of well-known traffic systems that use housenumbers in this manner include WO Traffic provided by WideOrbit Inc. ofSan Francisco, Calif., and OSi-Traffic™ provided by Harris Corporationof Melbourne, Fla.

Additional common attributes based on this standard include thoserelating to scheduling data. For example, a traffic log entry may have astart time that represents the intended start time for the correspondingVC, and a duration that represents the duration of the corresponding VC.Other common attributes may include, for example, a title that providesa description of the VC.

Still additional common attributes based on this standard include anepisode number, a segment number, and one or more auxiliary values. Theepisode number identifies a particular episode of a show, and isincluded in a traffic log entry that corresponds to a show-segment VC.The segment number identifies a particular segment number of a show, andis included in a traffic log entry that corresponds to a show-segmentVC. The one or more auxiliary values may be used for notes (e.g., suchthat a traffic manager may provide a note to a master control operatorabout the corresponding traffic log entry).

The above-described attributes are stored within corresponding fields inthe traffic log entry. For example, the house number is stored in ahouse-number field in the traffic log entry. Likewise, the one or moreauxiliary values are stored in one or more auxiliary-value fields in thetraffic log entry.

A traffic log typically spans a twenty-four hour period and is oftenreferred to as “daily” traffic log, although the traffic log often doesnot align with one calendar date. Instead, a traffic log typically spansfrom 5:00 am EST of one date to 5:00 am EST of the next date.Accordingly, a “Mar. 6, 2012 log” may span from 5:00 am EST on Tuesday,Mar. 6, 2012, to 5:00 am EST on Wednesday, Mar. 7, 2012.

While traffic log entries in a traffic log are often traversed asintended, in some instances it may be desired to deviate from thetraffic log as initially received. For example, in response to asporting event being delayed due to weather conditions, it may bedesired to make scheduling changes to and/or otherwise modify thetraffic log. As another example, in response to a breaking news event,it may be desired to interrupt the airing of a VC based on the trafficlog, and instead broadcast breaking news video coverage received from anewsroom production control room. Switching from a typical traversal oftraffic log entries in a traffic log to a feed from a newsroomproduction control room or other source is often referred to in theindustry as a “breakout.”

In one example, a bypass switcher in a MCS may be used to facilitate abreakout. The bypass switcher may be configured to map one of two inputsto an output, which may be connected to an air-chain system forbroadcast. In such a configuration, a first input may receive videoaccording to the traffic log, and the second input may receive videofrom a breakout source (e.g., a newsroom production control room asdescribed above). Therefore, by changing the mapping setting on thebypass switcher from the first input to the second input, the video fromthe breakout source will be broadcast instead of the video according tothe traffic log. Likewise, by changing the mapping setting back, videoaccording to the traffic log may again be broadcast.

The use of a bypass switcher to provide such breakout functionality maycause some undesired results. For example, the mapping setting on abypass switcher is typically one that is set manually. Therefore, a usermay need to manually change the mapping setting at the preciselyappropriate times (e.g., both when a breakout begins and when it ends).Also, while the breakout source may be sending the video that isactually being broadcast, the AS continues to traverse traffic logentries and channel corresponding VCs through one or more entities inthe MCS (although the VCs will not be sent through the bypass switcher,so they are not broadcast). As such the AS may be “unaware” that thebreakout has occurred. Among other things, this may cause issues inconnection with the as-run log, which is typically generated by an ASand serves to identify which VCs were actually broadcast for billing andother purposes. Since the AS may be unaware that VCs are not actuallyreaching the air-chain system, it may improperly identify a VC as beingbroadcast when that is not the case.

Finally, when the breakout is over, the process of rejoining the videoaccording to the traffic log (i.e., by reverting the mapping setting onthe bypass switcher to the first input), may result in an undesireddiscontinuity from the perspective of a viewer. Indeed, since the AScontinues to traverse traffic log entries during the breakout, dependingon when the breakout ends, the rejoining process may involve rejoiningin the middle of a VC (e.g., in the middle of a show-segment VC),potentially causing the view to be confused.

In one aspect of the presently disclosed system and method, in responseto a breakout, an AS may generate a simulation log, and may use thesimulation log to generate a missed list indicating VCs that are missedas a result of the breakout. Next, the AS may generate a custom log thatincludes one or more of the VCs indicated in the generated missed list.Then, the AS may leave the breakout, broadcast VCs in the custom log,and rejoin the traffic log using one or more rejoin techniques. Amongother things, this allows the AS to broadcast VCs that are missed due toa breakout in a timely manner. Further, by employing select rejointechniques, the AS may provide for a seamless transition from thebreakout to the custom log, and from the custom log to the traffic log.These and other aspects of the present system and method are describedin greater detail below.

II. Example Television-Broadcasting System

FIG. 1 shows an example television-broadcasting system, generallydesignated 100. The television-broadcasting system 100 may include atraffic system 200, a recording and playout system (RAPS) 300, a MCS400, and an air-chain system 500. The MCS 400 may serve as the hub ofthe television-broadcasting system 100 and may connect to each of thetraffic system 200, the RAPS 300, and the air-chain system 500.Generally, the television-broadcasting system 100 may be configured suchthat video may be sent from the RAPS 300 (or another source), throughthe MCS 400, and to the air-chain system 500 for television broadcast(e.g., over the air or over Internet Protocol (IP).

A. Traffic System

FIG. 2 shows the traffic system 200 in greater detail. The trafficsystem 200 may be configured for creating and sending a traffic log tothe MCS 300, and may include a data storage 202 and a communicationinterface 204, both of which may be connected to each other via aconnection mechanism (e.g., a bus) 206. The traffic system 200 may beconfigured to store traffic logs in the data storage 202, and to sendthe stored traffic logs, via the communication interface 204, to the MCS300. As discussed above, two example traffic systems are WO Trafficprovided by WideOrbit Inc. of San Francisco, Calif., and OSi-Traffic™provided by Harris Corporation of Melbourne, Fla.

B. RAPS

FIG. 3 shows the RAPS 300 in greater detail. The RAPS 300 may beconfigured to record and playout VCs for use by the MCS 400, and mayinclude a recording-and-playout device (RAPD) 302, a data storage 304, amanagement system 306, and a communication interface 308, each of whichmay be connected to each other via a connection mechanism 310.

The RAPD 302 may be configured to record VCs (e.g., a VC retrieved fromthe data storage 304) and playout (i.e. send) VCs, via the MCS 400, tothe air-chain system 500. The RAPD 302 may include a data storage 312and an output 314, both of which may be connected to each other by aconnection mechanism (not shown). The data storage 312 may be used forstoring VCs that may be sent via the output 314. The management system306 may be configured to manage the RAPD 302 by organizing and movingVCs back-and-forth between the RAPD and the data storage 304. Thecommunication interface 308 may connect the RAPS 300 to the MCS 400 orto another entity. An example of a RAPD is the K2 server provided byGrass Valley™ of San Francisco, Calif.

C. MCS

FIG. 4 shows the MCS 400 in greater detail. The MCS 400 may beconfigured to receive video (e.g., a VC sent from the RAPD or breakoutvideo sent from a breakout source 401), channel the video though one ormore entities, and send the video to the air-chain system 500 fortelevision broadcast. In one example, the MCS 400 includes a router 402,a stunt switcher 404, a bypass switcher 406, and an AS 408, each ofwhich may be connected to each other by a connection mechanism (notshown).

The router 402 may be configured to map two or more source entities totwo or more destination entities, and may include two or more inputs,including a first input 412 and a second input 414, and two or moreoutputs, including a first output 416 and a second output 418. Theinputs 412, 414, and the outputs 416, 418 may each be connected to eachother by a connection mechanism (not shown).

The RAPD 302 may be connected to the router 402 via the output 314 andthe input 412. The breakout source 401 may be connected to the router402 via an output 403 on the breakout source 401 and the input 414. Anexample of a router is the Blackmagic Design Videohub provided byBlackmagic Design Pty. Ltd. Of Fremont, Calif.

The stunt switcher 404 may be configured to map a source entity to adestination entity, and may include two or more inputs, including afirst input 420, and a second input 422, and two or more outputs,including a first output 424 and a second output 426. The stunt switchermay also include a data storage 428. The inputs 420, 422, the outputs424, 426, and the data storage 428 may each be connected to each otherby a connection mechanism (not shown).

The router 402 may be connected to the stunt switcher 404 via the output416 and the input 420. The router 402 may also be connected to the stuntswitcher 404 via the output 418 and the input 422. The stunt switcher404 may also be configured to provide graphical overlay and other videoeffects (sometimes referred to as “stunt work” or “digital videoeffects”) to received video before it is sent out. The stunt switchermay store effect data in the data storage 428. An example of a stuntswitcher is the Miranda NVISION NVS5100MC provided by NVision, Inc. ofCoppell, Tex.

The bypass switcher 406 may be configured to map a source entity to adestination entity. The bypass switcher 406 may include at least twoinputs including a first input 430 and a second input 432, and an output434, each of which may be connected to each other by a connectionmechanism (not shown). The stunt switcher 404 may be connected to thebypass switcher 406 via the output 424 and the input 430. The stuntswitcher 404 may also be connected to the bypass switcher 406 via theoutput 426 and the input 432.

Accordingly, provided that the router 402, the stunt switcher 404, andthe bypass switcher 406 all have the appropriate input-to-outputmappings, a VC sent from the RAPD 302 to the MCS 400 may be channeledthrough the entities in the MCS and sent out the MCS. Likewise, providedthat the router 402, the stunt switcher 404, and the bypass switcher 406all have the appropriate input-to-output mappings, video sent frombreakout source 401 to the MCS 400 may be channeled through the entitiesin the MCS and sent out the MCS.

The AS 410 may be configured to perform or to cause performance of oneor more functions related to the system 100. The AS 410 may include aprocessor 438, a data storage 440, a user-interface 442 (e.g., includinga display device), and a communication interface 444, all of which maybe connected by a connection mechanism (not shown). The processor 438may include one or more general-purpose processors (e.g.,microprocessors) and/or special-purpose processors (e.g., digital signalprocessors and/or application specific integrated circuits).

The data storage 440 may include one or more volatile and/ornon-volatile storage components and may be integrated in whole or inpart with the processor 438. The data storage 440 may take the form of anon-transitory computer-readable medium and may contain programinstructions, that when executed by the processor 438, cause performanceof one or more functions. For example, the AS 408 may cause the trafficsystem 200, the RAPS 300, the MCS 400, the air-chain system 500, anentity included therein, and/or another entity to perform one of more ofthe functions described in this disclosure. The AS 410 may cause suchfunctions to be performed by sending instructions and/or other data viaa corresponding communication interface and/or connection mechanism. TheAS 408 may receive data via the same path. In one example, the AS 408sends and receives data via a video disk control protocol (VDCP).

D. Air-Chain System

FIG. 5 shows the air-chain system 500 in greater detail. The air-chainsystem 500 may be configured to prepare and broadcast video receivedfrom the MCS 400 to a group of users. The air-chain system 500 mayinclude an encoder 502 and an OBD 504.

The encoder 502 may be configured to receive video from a source entity,generate a transport stream (TS) (that includes the video), and send thegenerated TS to a destination entity. The TS may be described asincluding video, meaning that the TS includes the encoded representationof the video, among other things. The encoder 502 may include an input506 and an output 508, each of which may be connected by a connectionmechanism (not shown). The bypass switcher 406 may be connected to theencoder 502 via the output 434 and the input 506.

In one example, the encoder 502 may generate a TS by, among otherthings, encoding video based on the high-definitionserial-digital-interface (HD-SDI) standard to video based on the MPEG 2standard. An example of an encoder is the NetVX provided by HarrisCorporation of Melbourne, Fla.

The OBD 504 may be configured to receive a TS from a source entity, andbroadcast the TS (i.e., including video) to multiple destinationentities. The OBD 504 may include an input 510, and the encoder 502 maybe connected to the OBD via the output 508 and the input 510. The OBD504 may be a transmitter, satellite, terrestrial fiber transmitter, ornetwork connection (e.g., for an Internet feed) that may correspond witha service provider.

The television-broadcasting system 100 described above is onenon-limiting example. Indeed, the presently disclosed system may includesome or all of the entities discussed above, and may be arranged indifferent ways as would be apparent to one of ordinary skill in the art.As one example, in the MCS 400, the breakout source 401 may connectdirectly to the bypass switcher 406 (i.e., omitting the router 402 andthe stunt switcher 404). As another example, the data storage 304 andthe management system 306 may be included in the MCS 400, rather than inthe RAPS 300.

III. First Set of Example Methods

FIG. 6 (parts A and B) shows a flow chart illustrating functions inaccordance with a first set of example methods. At block 602, the methodmay involve the AS 408 receiving a traffic log from the traffic system200.

The traffic log may include traffic log entries, each corresponding to aVC and a start time. The start time may be specified in a variety ofways, such as in an hour::minute::second format or anhour::minute::second::frame format. However, for simplicity, start timeswill be referenced in this disclosure using whole numbers representingunits of time. For example, a first traffic log entry may correspond toa VC A and a start time 0, and a second traffic log entry may correspondto a VC B and a start time 5. As such, the VC B is scheduled to start 5time units (e.g., minutes) after the VC A.

FIG. 7 shows an example traffic timeline 702 based on an example trafficlog. The traffic timeline 702 shows VCs A-G, each with correspondingstart times. As indicated by the “key” 704, select VCs are show-segmentVCs (namely, the VCs A, D, and G), and selected VCs are commercial VCs(namely, the VCs B, C, E, and F). The traffic timeline 702 may beappropriately described as an “expected” traffic timeline since abreakout event may cause other video (i.e., not in accordance with thetraffic log) to be broadcast. For clarity, the video that is actuallybroadcast is shown by way of an as-run timeline, an example of which isalso shown in FIG. 7, and which is generally designated 706. Notably,since the as-run logs described herein reflect what video is actuallybeing broadcast, these may be used for billing and other relatedpurposes. Difference between the traffic timeline 702 and the as-runtimeline 706 (resulting from a breakout) are discussed in greater detailbelow.

At block 604, the method may involve the AS 408 operating in a trafficlog mode. As used throughout this disclosure, operating in a mode refersto performing one or more functions associated with that mode, examplesof which are described herein. The AS 408 operating in the traffic logmode may involve the AS 408 traversing the traffic log entries accordingto the corresponding start times and a running time (e.g., provided by aclock), and sending the VCs corresponding to the traversed traffic logentries to the air-chain system 500 in sequence (as the traffic logentries are traversed). For example, as shown up to the time 5.5 in theas-run timeline 706, the AS 408 operates in the traffic log mode suchthat the VC A and a portion of the VC B are traversed and sent to theair-chain system 500 for broadcast. As shown in the as-run timeline 706(and other timelines), a portion of a VC is represented with a “′”(e.g., B′ indicates that a portion of the VC B is broadcast).

At block 606, the method may involve the AS 408 receiving abreakout-mode request. In one example, the breakout-mode request may bereceived from a user via the user interface 442. As such, a mastercontrol operator may determine that a breakout is appropriate (e.g., inresponse to receiving a notification that video from a newsroomproduction control room should be broadcast instead of the VCs accordingto the traffic log), and therefore the operator may request that the AS408 operate in a breakout mode. In one example, the AS 408 may alsoreceive a selection of a particular breakout source to be used for thebreakout, again such as via the user interface 442. Notably, while therouter 402 is shown connected to one breakout source 401, the router 402may be connected to additional breakout sources (via additional inputs)as desired. A breakout source may be any source that may send video,including for example a newsroom production control room or a satellite.

Responsive to the AS 408 receiving the breakout-mode request, the AS mayperform the functions in blocks 608, 610, and 612. At block 608, themethod may involve the AS 408 terminating operation of the traffic logmode. At block 610, the method may involve the AS 408 generating asimulation log that includes simulation entries, and that is a copy ofat least a portion of the traffic log. In one example, the generatedsimulation log may be a copy of the traffic log starting at the positionwhere the traffic log mode was terminated (i.e., at time 5.5 in theexample represented in FIG. 7) and ending at the end of the traffic log(i.e., at time 16 in the example represented in FIG. 7). An examplesimulation timeline based on the simulation log is generally designated708.

At block 612, the method may involve the AS 408 operating in a breakoutmode. The AS 408 operating in the breakout mode may involve one or morefunctions. In one example, the AS 408 operating in the breakout modeinvolves four functions.

First, the AS 408 operating in the breakout mode may involve the ASsending video received from the breakout source 401 to the air-chainsystem 500. In an example where multiple breakout sources are connectedto the router 402, video received from a selected breakout source may besent to the air-chain system 500. In either case, the AS 408 may performthis function by changing the mapping settings on one or more of therouter 402, the stunt switcher 404, and the bypass switcher 406 asappropriate such that the video from the breakout source 401 is sent outthe MCS 400.

Second, the AS 408 operating in the breakout mode may involve the AStraversing the simulation entries according to the corresponding starttimes and the (running) time.

Third, the AS operating in the breakout mode may involve the ASgenerating a missed list that indicates the VCs corresponding to thetraversed simulation entries. For example, as shown on the as-runtimeline 706, in the event that the AS 408 operates in the breakout modefrom the time 5.5 to the time 11.5, the AS 408 may traverse a portion ofthe VC B, the entire VC C, and a portion of the VC D. Accordingly, anindication of the VCs B, C, and D may be added to the generated missedlist. The generated missed list therefore represents VCs that werescheduled to be broadcast, but which were not due to the breakout, andthat may be desired to be scheduled again following the breakout.

In one example, the generated missed list may include any VCcorresponding to the traversed simulation entries, that is, includingthose that were partially broadcast, such as VCs B and D in the exampleprovided above. However, in another example, the generated missed listmay only include VCs corresponding to the traversed simulation entrieswhere no portion of the VC was broadcast. In yet another example, thedetermination as to whether to include such partially broadcast VCs maydepend on the type of VC and/or the portion of the VC that wasbroadcast. For instance, a commercial VC may only be added to thegenerated missed list if less than 75% of the commercial VC wasbroadcast. This may reflect an agreement between the broadcastingcompany and the commercial VC provider that provides that thebroadcasting company will only be paid if at least 75% of the commercialis broadcast. As such, if less than 75% if broadcast, the commercial VCmay appropriately be added to the generated missed list such that it canbe broadcast again in its entirety.

Fourth, the AS 408 operating in the breakout mode may involve the ASgenerating a custom log that includes at least a portion of the VCs inthe generated missed list. The custom log indicates VCs that, asdescribed in greater detail below, are broadcast after the AS 408terminates operating in the breakout mode, but before the AS startsoperating in the traffic log mode again (i.e., before a “rejoin” of thetraffic log mode).

In one example, the generated missed list may be displayed via the userinterface 442, such as for viewing by a master control operator suchthat the operator may select VCs from the missed list for inclusion inthe custom log. Related data, such as the total duration of the VCsindicated in the custom log may also be determined and displayed.Accordingly, the AS 408 may receive custom VC selections via the userinterface 442. In one example, the user interface 442 may take the formof a graphical user interface configured to allow the user to drag anddrop VCs from the missed list into the custom log. The user interface442 may also be configured to allow the user to search for and add oneor more additional VCs that are not included in the missed list (e.g.,those stored in the data storage 304) to the generated custom log,and/or otherwise edit the custom log (e.g., change the order of VCs,etc.) In one example, the user interface may allow custom logs to bestored or retrieved (e.g., in and from the data storage 440).

At block 614, the method may involve the AS 408 receiving a rejoinrequest. In one example, the AS 408 receives the rejoin request from auser via the user interface 442. A rejoin request may include one ofseveral potential types of rejoin requests, three examples of which areprovided. A first example is a request to rejoin the traffic log inprogress. A second example is a request to rejoin the traffic log at aforced start of a target show-segment VC corresponding to a traffic logentry in the traffic log. A third example is a request to rejoin thetraffic log at a natural start of a target show-segment VC correspondingto a traffic log entry in the traffic log.

Additional functions at blocks 616, 618, 620, and 622 of the method willnow be described. Notably, one or more of these functions may includevariations depending on the type of rejoin request received at block614. Accordingly, these functions will be initially provided, and thendescribed in greater detail in connection with techniques correspondingto each of three example rejoin requests provided above.

At block 616, the method may involve the AS 408 determining a breakouttermination time based on the received rejoin request.

At block 618, the method may involve proximate (i.e., temporallyproximate or near) the determined breakout termination time, the AS 408terminating operation of the breakout-mode, and operating in a customlog mode. The AS 408 operating in the custom log mode may involve the AS408 traversing and sending VCs indicated in the generated custom log tothe air-chain system 500 in sequence.

At block 620, the method may involve the AS 408 determining a rejoinposition of the traffic log based on the received rejoin request.

At block 622, the method may involve the AS 408 operating in the trafficlog mode (again), except that the traffic log entries are traversedstarting at the determined rejoin position.

A. First Rejoin Technique—Rejoin in Progress

An example where the AS 408 receives a request to rejoin the traffic login progress will now be described. This example allows for the AS 408 torejoin the traffic log at a position where the traffic log would havebeen had there not been a breakout, and will be described in connectionwith the as-run timeline 706.

Recall that, as a result of the AS 408 operating in the traffic logmode, the VC A and a portion of the VC B are broadcast as shown in theas-run timeline 706. Likewise, as a result of the AS 408 terminating thetraffic log mode, and operating in a breakout mode, video from thebreakout source 401 interrupts the VC sequencing, and is broadcast(starting at time 5.5) as shown in the as-run timeline 706.

In one example, in response to the AS 408 receiving the request torejoin the traffic log in progress, the function at block 616 mayinvolve the AS 408 determining that a breakout termination time is thetime that the rejoin request is received. This may allow a user to senda request to the AS 408 (e.g., via the user interface 442), therebycausing the AS to immediately perform the function at block 618 ofterminating operation of the breakout-mode, and operating in a customlog mode. This change of functions is shown at the time 11.5 in theas-run timeline 706.

The AS 408 then operates in the custom log mode, traversing and sendingthe VCs indicated in the generated custom log to the air-chain system500 in sequence. In the example provided, the generated custom logindicates the VCs B and C, each of which have a duration of one minute.Accordingly, the total duration of the VCs indicated in the custom logis two minutes, and therefore the AS 408 operates in the custom log modefor two minutes, or until the time 13.5 as shown in the as-run timeline706. Notably, the AS 408 may terminate operation of the custom log modeonce each corresponding VC is traversed and sent to the air-chain system500.

The function at block 620 may involve the AS 408 determining that arejoin position of the traffic log is a position of the traffic log thatcorresponds to the time when the custom log terminates. As such, at thetime 13.5, the AS determines that a rejoin position of the traffic logis a position of the traffic log that corresponds to the time 13.5. Asshown in traffic timeline 702, the time 13.5 corresponds to a positionthat is halfway through the VC F. Accordingly, the function at block 622involves operating in the traffic log mode (again), except that thetraffic log entries are traversed starting halfway through VS F,followed by the VC G and any subsequent VCs (not shown) in the trafficlog.

B. Second Rejoin Technique—Rejoin at a Forced Start of a Show-Segment VC

An example where the AS 408 receives a request to rejoin the traffic logat a forced start of a target show-segment VC corresponding to a trafficlog entry in the traffic log will now be described. This example allowsfor the AS 408 to rejoin the traffic log at a forced position in thetraffic log, namely at the start of a target show-segment VC. This mayprovide a seamless rejoin experience for the user as opposed to forexample, where the rejoin occurs in the middle of a VC. This examplewill be described in connection with an as-run timeline 806 as shown inFIG. 8. Notably, the as-run timeline 806 is still based on the trafficlog timeline 702, the key 704, and the simulation timeline 708, whichare therefore also included in FIG. 8.

The functions described in connection with the forced start rejointechnique are the same as in connection with the rejoin in progresstechnique up to the function at block 618, and therefore those functionsare not repeated. Accordingly, the functions at blocks 620, and 622 willnow be described.

The function at block 620 may involve the AS 408 determining that arejoin position of the traffic log is a start of a target show-segmentVC corresponding to the target traffic log entry in the traffic log. Forthe purposes of this example, assume that the target show-segment VC isthe VC G (based on a master control operator selecting the VC G via theuser interface 442). However, as shown in the as-run timeline 806, sincethe AS 408 concludes operation of the custom log mode at the time 13.5,and the VC G is not scheduled to start until the time 14, the start timecorresponding to the VC G (and any subsequent VCs) must be modified tomaintain a sequential and seamless broadcast.

Accordingly, the start times of the traffic log entry corresponding tothe target show-segment VC, and any subsequent traffic log entries aremodified such that they are reduced by a displacement time. Thedisplacement time is the start time of the target show-segment VC minusthe time when the AS 408 terminates operation of the custom log. Asshown in the as-run timeline 806, the start time of the VC G is 14 andthe time when operation of the custom log terminates is 13.5.Accordingly, the displacement time is 0.5, and therefore the start timeof the VC G and any subsequent VCs have a start time moved up by 0.5.Notably, the traffic log may need to be “corrected” eventually to makefor this displacement time.

C. Third Rejoin Technique—Rejoin at a Natural Start of a Show-Segment VC

An example where the AS 408 receives a request to rejoin the traffic logat a natural start of a target show-segment VC corresponding to atraffic log entry in the traffic log will now be described. This exampleallows for the AS 408 to rejoin the traffic log at a position where thetraffic log would have been had there not been a breakout, but wherethat position has a particular characteristic, namely that it is thetime where a show-segment VC starts. Like the example above, this mayprovide a seamless rejoin experience for the user. However, since thenatural start time of the target show-segment VC is used, the rejoindoes not create the need for subsequent log entries to be rescheduled(e.g., using the displacement time as discussed above).

This example will be described in connection with an as-run timeline 906as shown in FIG. 9. Notably, the as-run timeline 906 is still based onthe traffic log timeline 702, the key 704, and the simulation timeline708, which are therefore also included in FIG. 9.

The functions described in connection with the forced start-time exampleare the same as in connection with this example, except in connectionwith blocks 616 and 622. Accordingly, the functions at blocks 616 and622 will now be described in greater detail.

The function at block 616 may involve the AS 408 determining that abreakout termination time is a start time corresponding to the targetshow-segment VC minus a total duration of the VCs indicated in thecustom log. As such, assuming again in this example that the targetshow-segment VC is the VC G, and that the custom log indicates the VCs Band C, the start time of the target show-segment VC is 14 and the totalduration of the indicated VCs in the custom log is 2. Accordingly, thebreakout termination time is 12 as shown in the as-run log 906.

In one example, the method may further involve the AS 408 determining aremaining breakout time by subtracting the breakout termination timefrom the time when the remaining breakout time is determined. Forexample, at the time 10, the remaining breakout time would be 2. In oneexample, the method may involve displaying the remaining breakout timevia the user interface 442. The user interface 442 may be accessible tothe newsroom production control room, such that newscasters or otherusers may be provided with a countdown indicating when the breakoutshould end.

The function at block 622 may involve the AS 408 operating in thetraffic log mode (again), except that the traffic log entries aretraversed starting at the beginning of the VC G, followed by anysubsequent VCs (not shown) in the traffic log. However, unlike in therejoin with a forced start technique, the start times of the traffic logentry corresponding to the target show-segment VC, and any subsequenttraffic log entries need not be modified.

V. Example Variations

Following the AS 408 operating in the breakout mode, as an alternativeto rejoining the traffic log mode, the AS may instead “extend” thebreakout using one or more of the techniques described in thecross-referenced U.S. application Ser. No. 13/629,519, entitled “Systemand Method for Extending a Breakout in a Broadcasting Environment.”

While each of the examples discussed above provide for the AS 408operating in a custom log mode (after operating in the breakout mode,and before rejoining the traffic log mode), in some examples, thefunction of operating in the custom log mode may be omitted. Notably, inthe rejoin at the natural start time technique, this change may affectthe determination of the breakout termination time (which no longerneeds to account for the total duration of the VCs indicated in thegenerated custom log). Further, in such examples, select relatedfunctions (e.g., generating the simulated log, generating the missedlist, and generating the custom list) may be omitted.

While examples have been described in terms of VCs for use in atelevision-broadcasting environment, the presently disclosed system andmethod may also be adapted for use with other multi-user distributionenvironments, including for example, a radio-broadcasting environment.Like a television-broadcasting system, a radio-broadcasting systems alsoinclude a traffic system (that also create traffic logs with entries),and other entities that parallel those in a television-broadcastingsystem. However, radio-broadcasting system supports audio, but notvideo. Therefore, radio-broadcasting systems may be adapted for use withaudio-components (AC) rather than VCs. As a result, select entitiesand/or functions and described throughout this disclosure may be adaptedaccordingly (e.g., a breakout source may send audio rather than video).Notably, the term MC (and related terms, such as an evergreen MC) mayrefer to either an AC or a VC. In another example, the presentlydisclosed system and method may be adapted for use with anInternet-broadcasting environment (e.g., an environment in which MCs arebroadcast over IP to end-user devices). The term broadcast as used inthis disclosure also includes multicast.

While one or more functions of the presently disclosed method have beendescribed as being performed by the certain entities (e.g., the AS 408),the functions may be performed by any entity, such as those included inthe television-broadcasting system 100 described above. Further, thedescribed steps throughout this application need not be performed in thedisclosed order, although in some examples, an order may be preferred.Also, not all steps need to be performed to achieve the desiredadvantages of the presently disclosed system and method, and thereforenot all steps are required.

Further, while examples have been described in terms of selectembodiments, alterations and permutations of these embodiments will beapparent to those of ordinary skill in the art. For example, the use oflogical structures including loops and condition statements can bemodified, interchanged, or restricted without departing from thepresently disclosed system and method. Other changes, substitutions, andalterations are also possible without departing from the presentlydisclosed system and method in its broader aspects as set forth in thefollowing claims.

The invention claimed is:
 1. A method for sending video to an air-chainsystem for television broadcast, the method comprising: receiving from atraffic system, a traffic log including traffic log entries, eachcorresponding to a video component (VC) and a start time; operating in atraffic log mode comprising: traversing the traffic log entriesaccording to the corresponding start times and a running time, andsending the VCs corresponding to the traversed traffic log entries tothe air-chain system in sequence; receiving a breakout-mode request;responsive to receiving the breakout-mode request, (i) terminatingoperation of the traffic log mode, (ii) generating a simulation log thatincludes simulation entries, and that is a copy of at least a portion ofthe traffic log, and (iii) operating in a breakout mode comprising: (a)sending video received from a breakout source to the air-chain system,(b) traversing the simulation entries according to the correspondingstart times and a current time, (c) generating a missed list thatindicates the VCs corresponding to the traversed simulation entries, and(d) generating a custom log that indicates at least a portion of the VCsin the generated missed list; receiving a rejoin request; determining abreakout termination time based on the received rejoin request;proximate the breakout termination time, terminating operation of thebreakout-mode, and operating in a custom log mode comprising traversingand sending the VCs indicated in the generated custom log to theair-chain system in sequence; determining a rejoin position of thetraffic log based on the received rejoin request; and operating in thetraffic log mode, wherein the traffic log entries are traversed startingat the determined rejoin position.
 2. The method of claim 1, whereinreceiving the rejoin request comprises receiving a request to rejoin thetraffic log in progress, and wherein determining the rejoin positioncomprises determining that the rejoin position is a position of thetraffic log that corresponds to the time when the custom log modeterminates.
 3. The method of claim 2, wherein determining the breakouttermination time comprises determining that the breakout terminationtime is the time that the rejoin request is received.
 4. The method ofclaim 1, wherein receiving the rejoin request comprises receiving arequest to rejoin the traffic log at a forced start of a targetshow-segment VC corresponding to a traffic log entry in the traffic log,wherein determining the rejoin position comprises determining that therejoin position is a start of the target show-segment VC, wherein starttimes of the traffic log entry corresponding to the target show-segmentVC and any subsequent traffic log entries are modified such that theyare reduced by a displacement time, wherein the displacement time is thestart time of the target show-segment VC minus the time when operationof the custom log mode terminates.
 5. The method of claim 4, whereindetermining the breakout termination time comprises determining that thebreakout termination time is the time when the rejoin request isreceived.
 6. The method of claim 1, wherein receiving the rejoin requestcomprises receiving a request to rejoin the traffic log at a naturalstart of a show-segment VC corresponding to a target log entry in thetraffic log, and wherein determining the breakout termination timecomprises determining that the breakout termination time is a start timecorresponding to the target show-segment VC minus a total duration ofthe VCs indicated in the custom log.
 7. The method of claim 6, furthercomprising: determining a remaining breakout time that is the determinedbreakout termination time minus the time when the remaining breakouttime is determined; and displaying the remaining breakout time on a userinterface.
 8. The method of claim 1, wherein receiving the breakout-moderequest comprises receiving the breakout mode request via a userinterface, and wherein receiving the rejoin request comprises receivingthe rejoin request via the user interface.
 9. The method of claim 1,further comprising: displaying the missed list on a user interface; andreceiving custom VC selections via the user interface; whereingenerating the custom log comprises generating the custom log using thereceived custom VC selections.
 10. A non-transitory computer-readablemedium containing instructions that, when executed by a processor, causea set of functions to be performed, the set comprising: receiving from atraffic system, a traffic log including traffic log entries, eachcorresponding to a video component (VC) and a start time; operating in atraffic log mode comprising: traversing the traffic log entriesaccording to the corresponding start times and a running time, andsending the VCs corresponding to the traversed traffic log entries to anair-chain system in sequence; receiving a breakout-mode request;responsive to receiving the breakout-mode request, (i) terminatingoperation of the traffic log mode, (ii) generating a simulation log thatincludes simulation entries, and that is a copy of at least a portion ofthe traffic log, and (iii) operating in a breakout mode comprising: (a)sending video received from a breakout source to the air-chain system,(b) traversing the simulation entries according to the correspondingstart times and a current time, (c) generating a missed list thatindicates the VCs corresponding to the traversed simulation entries, and(d) generating a custom log that indicates at least a portion of the VCsin the generated missed list; receiving a rejoin request; determining abreakout termination time based on the received rejoin request;proximate the breakout termination time, terminating operation of thebreakout-mode, and operating in a custom log mode comprising traversingand sending the VCs indicated in the generated custom log to theair-chain system in sequence; determining a rejoin position of thetraffic log based on the received rejoin request; and operating in thetraffic log mode, wherein the traffic log entries are traversed startingat the determined rejoin position.
 11. The computer-readable medium ofclaim 10, wherein receiving the rejoin request comprises receiving arequest to rejoin the traffic log in progress, and wherein determiningthe rejoin position comprises determining that the rejoin position is aposition of the traffic log that corresponds to the time when the customlog mode terminates.
 12. The computer-readable medium of claim 11,wherein determining the breakout termination time comprises determiningthat the breakout termination time is the time that the rejoin requestis received.
 13. The computer-readable medium of claim 10, whereinreceiving the rejoin request comprises receiving a request to rejoin thetraffic log at a forced start of a target show-segment VC correspondingto a traffic log entry in the traffic log, wherein determining therejoin position comprises determining that the rejoin position is astart of the target show-segment VC, wherein start times of the trafficlog entry corresponding to the target show-segment VC and any subsequenttraffic log entries are modified such that they are reduced by adisplacement time, wherein the displacement time is the start time ofthe target show-segment VC minus the time when operation of the customlog mode terminates.
 14. The computer-readable medium of claim 13,wherein determining the breakout termination time comprises determiningthat the breakout termination time is the time when the rejoin requestis received.
 15. The computer-readable medium of claim 10, whereinreceiving the rejoin request comprises receiving a request to rejoin thetraffic log at a natural start of a show-segment VC corresponding to atarget log entry in the traffic log, and wherein determining thebreakout termination time comprises determining that the breakouttermination time is a start time corresponding to the targetshow-segment VC minus a total duration of the VCs indicated in thecustom log.
 16. The computer-readable medium of claim 15, the setfurther comprising: determining a remaining breakout time that is thedetermined breakout termination time minus the time when the remainingbreakout time is determined; and displaying the remaining breakout timeon a user interface.
 17. The computer-readable medium of claim 10,wherein receiving the breakout-mode request comprises receiving thebreakout mode request via a user interface, and wherein receiving therejoin request comprises receiving the rejoin request via the userinterface.
 18. The computer-readable medium of claim 10, the set furthercomprising: displaying the missed list on a user interface; andreceiving custom VC selections via the user interface; whereingenerating the custom log comprises generating the custom log using thereceived custom VC selections.
 19. A method for sending audio to anair-chain system for radio broadcast, the method comprising: receivingfrom a traffic system, a traffic log including traffic log entries, eachcorresponding to an audio component (AC) and a start time; operating ina traffic log mode comprising: traversing the traffic log entriesaccording to the corresponding start times and a running time, andsending the ACs corresponding to the traversed traffic log entries tothe air-chain system in sequence; receiving a breakout-mode request;responsive to receiving the breakout-mode request, (i) terminatingoperation of the traffic log mode, (ii) generating a simulation log thatincludes simulation entries, and that is a copy of at least a portion ofthe traffic log, and (iii) operating in a breakout mode comprising: (a)sending audio received from a breakout source to the air-chain system,(b) traversing the simulation entries according to the correspondingstart times and a current time, (c) generating a missed list thatindicates the ACs corresponding to the traversed simulation entries, and(d) generating a custom log that indicates at least a portion of the ACsin the generated missed list; receiving a rejoin request; determining abreakout termination time based on the received rejoin request;proximate the breakout termination time, terminating operation of thebreakout-mode, and operating in a custom log mode comprising traversingand sending the ACs indicated in the generated custom log to theair-chain system in sequence; determining a rejoin position of thetraffic log based on the received rejoin request; and operating in thetraffic log mode, wherein the traffic log entries are traversed startingat the determined rejoin position.
 20. The method of claim 19, whereinreceiving the rejoin request comprises receiving a request to rejoin thetraffic log at a natural start of a show-segment AC corresponding to atarget log entry in the traffic log, and wherein determining thebreakout termination time comprises determining that the breakouttermination time is a start time corresponding to the targetshow-segment AC minus a total duration of the ACs indicated in thecustom log.